Realtime land use rights management

ABSTRACT

Land use rights management where land use rights are represented as bounded space, and portions of rights are represented as portions of whole rights. The portions are specifically designated subspaces within the bounded space. Tracking land use rights conveyance with the representations includes tracking conveyances as subdivisions of whole or partial subspaces within the bounded space, each subspace also bounded. The management system can compute subdivisions with set operations on the subspaces and bounded space.

PRIORITY

This application is a nonprovisional of, and claims the benefit ofpriority of, U.S. Provisional Patent Application No. 62/293,348, filedFeb. 10, 2016. That application is hereby incorporated by reference.

FIELD

Descriptions herein relate generally to property and land use rightstracking, and more particular descriptions are related to realtime tractrights management based on weighting land use rights instead of usingscalar percentages.

COPYRIGHT NOTICE/PERMISSION

Portions of the disclosure of this patent document can contain materialthat is subject to copyright protection. The copyright owner has noobjection to the reproduction by anyone of the patent document or thepatent disclosure as it appears in the Patent and Trademark Officepatent file or records, but otherwise reserves all copyright rightswhatsoever. The copyright notice applies to all data as described below,and in the accompanying drawings hereto, as well as to any softwaredescribed below: Copyright © 2016, Tract.co. All Rights Reserved.

BACKGROUND

Real property ownership has long been the basis of wealth in humansociety. Real property ownership can accompany certain rights to use theland that is the subject of the real property ownership. One right thathas long been part of the governance of real property is surface andmineral ownership rights. Mineral ownership is traditionally made up ofmultiple different rights, often referred to a “bundle of sticks.” Suchsticks or rights can include: Executive rights, or the right to lease;Bonus rights, or the right to receive bonus; Delay rights, or the rightto receive delay rentals; Royalty rights, or the right to receiveroyalty; and, Ingress/Egress rights, or the right to enter property.

Each right can be severed from any other, and can be separately conveyedor reserved. Each right ties back to the other. In addition to beingable to separately convey individual rights, each right can be conveyedin whole or in part, and based on specified extents of horizontalproperty coordinates (i.e., specified plots), depth, in time, andseparately for different minerals. The conveyances can thus result inmultidimensional tracking problems, where each separate right can beconveyed in any of the other dimensions or axes of extent of conveyance.

Natural human understanding is generally limited to conceptualizing inthree dimensions, since we are familiar with three dimensional space.However, when property rights management can involve five or sixdimensions, depending on how the rights are split, it is outside normalhuman conceptual understanding. As a result, despite hundreds of yearsof such property rights conveyances, there are no solutions to guaranteethat the conveying party has the ability to convey the exact rightspromised.

Thus, throughout history and even today, interest is error prone andtracked totally by hand. The modern creation of spreadsheets has broughtmore order to the issue, but the author must traditionally set to memorythe individual's names and aliases and do the best job they can oftracking the interest throughout time as mergers of interest collideacross the title chain. All forms of charts are complicated and nearlyimpossible to interpret or follow, and do not enable the naturaltracking of all possible dimensions.

BRIEF DESCRIPTION OF THE DRAWINGS

The following description includes discussion of figures havingillustrations given by way of example of implementations of embodimentsdescribed. The drawings should be understood by way of example, and notby way of limitation. As used herein, references to one or more“embodiments” are to be understood as describing a particular feature,structure, or characteristic included in at least one implementation.Thus, phrases such as “in one embodiment” or “in an alternateembodiment” appearing herein describe various embodiments andimplementations, and do not necessarily all refer to the sameembodiment. However, they are also not necessarily mutually exclusive.

FIG. 1A is a representation of an embodiment of a conveyance flowchartillustrating influence of one conveyance document over another portionof the chain of title.

FIG. 1B is a representation of an embodiment of a conveyance flowchartillustrating ownership in accordance with interval sets.

FIG. 2 is a representation of an embodiment of conveyance information inaccordance with interval sets where a management system computesrelationships based on set operations.

FIG. 3 is a block diagram of an embodiment of a management system.

FIG. 4 is a representation of an embodiment of a treehouse view.

FIG. 5 is a representation of an alternative embodiment of the treehouseview.

FIG. 6 is an embodiment of a flow diagram of a process for computingland use rights based on conveyance information.

FIG. 7 is an embodiment of a flow diagram of a process for generating agraphical rendering of land use rights information.

FIG. 8A is a representation of an embodiment of a standard graphicalconveyance view.

FIG. 8B is a representation of an embodiment of a standard graphicalconveyance view showing highlighted relationships.

FIGS. 9A-9B illustrate a representation of an embodiment of a graphicallayered view.

FIG. 10 is a representation of an embodiment of a graphical conveyanceview illustrating the timing of conveyances.

FIG. 11 is a representation of an embodiment of a graphical ownershipreport.

FIG. 12 is a representation of an embodiment of a graphical runsheetreport.

FIG. 13 is a representation of an embodiment of pseudocode for aconveyance management engine.

FIG. 14 is a representation of an embodiment of pseudocode for a displayof a conveyance management engine.

FIG. 15 is a block of an embodiment of a conveyance object with weightedrights management.

FIG. 16 is a block diagram of an embodiment of a computing system inwhich real property rights management can be implemented.

FIG. 17 is a block diagram of an embodiment of a mobile device in whichreal property rights management can be implemented.

FIG. 18 is a block diagram of an embodiment of a multi-node network inwhich real property rights management can be implemented.

Descriptions of certain details and embodiments follow, including adescription of the figures, which can depict some or all of theembodiments described below, as well as discussing other potentialembodiments or implementations of the inventive concepts presentedherein.

DETAILED DESCRIPTION

As described herein, a system provides realtime land use rightsmanagement. The realtime land use rights management represents in realtime the conveyance information entered. The system computes chain oftitle information in multidimensional space to provide an accuraterepresentation of rights conveyed. The system can implement land rightsobjects that include properties that have ranges of affected rights. Inone embodiment, the system generates an interactive graphical model ofthe chain of title. Such a model can be or include a flowchartillustrating conveyance information and relationships between conveyanceinstruments. The system can compute and graphically representrelationships between conveyance instruments or documents. In oneembodiment, the graphical representations include lines or othergraphical relationships connecting conveyance instruments to indicateinfluence of one instrument to other instruments downstream (later intime) and/or show influence based on source (documents earlier in time).

In one embodiment, the management system includes computer equipmentconfigured to execute a management engine. The management engineincludes configuration to compute conveyance information in multipledimensions. In one embodiment, the management engine generates objectsthat manage the multidimensional conveyance information andrelationships. In one embodiment, the management system includes arendering engine to generate a graphical representation of theconveyance information.

The management system represents a land use right as a bounded space. Inone embodiment, the system generates or modifies one or more objectsthat include the bounded space information as operable properties of theobject. The object can be generated as multiple instances to representdistinct transactions and historical documents related to the propertyrights. The object instances can include relationships that manage theinfluence of one transaction on another, including traceable rights tosource and to children or progeny of the documents, referring toconveyance transactions and information that comes later in time.

Within the management system, the right can be conveyed in whole or inpart, and the management system creates a representation of a partialright as a portion of the whole right, which is a specificallydesignated subspaces within the bounded space. In one embodiment, thepartial right is represented as an interval, or a vector, or otherweighted object, which includes specific upper and lower bounds withinthe bounded space. For example, the whole bounded space can berepresented as having an interval of 1.0, and a half portion can have aninterval of 0.5. However, instead of only having a scalar value torepresent the amount of the portion, as has previously been done, themanagement system represents a half portion specifically by the upperand lower bounds of the conveyance. For example, a half portion can bean interval of 0 to 0.5, or 0.25 to 0.75. Thus, the management systemcan accurately track not only the scalar amounts of conveyances, butalso preserve the precise rights conveyed. By making the specificintervals be operable properties of the weighted object, the system cantrack whole or partial conveyance of specific rights across multipledimensions, and represent the information in a manner that is trackableand understandable to a person.

Consider a specific example where A has 100% of the executive right andB has 100% of the royalty of the exact same plot of land. B has no rightto lease, but only to receive a Royalty from the lease that A signs. Themanagement system can represent A's rights as 0-1 for executive rightsof a specific plot of land, and B's rights as 0-1 for royalty rights forthe same plot. As the example stands, there is little confusion.However, if A and/or B further convey portions of rights to otherparties who may then also convey all or portions of rights, and certainparties convey rights to each other, it can become difficult if notimpossible to track who has what rights. However, the management systemcan keep track of specific conveyances and preserve the conveyanceinformation through the entire chain of title.

Consider a second specific example where A has 100% of everything andconveys 50% to B and 50% to C. B then severs the Executive right andconveys it to C. If C later severs his executive right and gives it toB, when C signs a lease he is now leasing B's Royalty and when B signs alease he is leasing C's Royalty. The royalty and the executive rightstie directly back to the original interest they were severed from. Thisis a relatively simple example considering it deals with only thesevering of two rights from the whole, and considering a single plot ofland.

However, in practice all rights can be severed on any axis andthroughout time, which can create a 6 dimensional space to be tracked.The axes of the 6 dimensional space can include an x-axis and a y-axisindicating horizontal or acreage splits, a z-axis indicating depth orformation, a t-axis indicating time, an m-axis indicating mineral type,and an r-axis indicating type of right. An example of x-axis and y-axissevering can include A conveying the Southeast quarter of a 10-acretract named Whiteacre to B. An example of a z-axis severance is that anyone or more of the rights can be conveyed for any depth (e.g.,1000′-2000′) or formation (the Eagleford Resource formation). An exampleof a t-axis severance can include C conveying a 5-year term lease or alife estate to D. An example of an m-axis severance can include Econveying rights for any one or more (separately or together) of oil,gas, coal, or other mineral rights, or a combination. The r-axis canalso be referred to as an “interest axis,” referring to how muchinterest is owned in each of the “bundle of sticks.”

In one embodiment, the management system tracks each element ofinformation about mineral ownership and/or other land use rights andrelates them to each other. In one embodiment, the management systemrepresents each mineral ownership or land use right ownership as aninterval on the real number line. For example, the management system canuse any consecutive interval as defined in the system, such as theinterval from 0 to 1 to represent 100% ownership of a specific right.Such a system using the interval from 0 to 1 can subdivide the ownershipinto portions of the whole, for example, down to hundredths (0.01granularity) or thousandths (0.001 granularity). Alternatively, a systemcould use an interval of 0 to 100, 0 to 1000, or other interval as willbe understood by those skilled in the art. The intervals create abounded space to represent ownership of a right.

For any conveyance of rights, the management system can apportion orrepresent the conveyance as a specific sub-portion or sub-interval ofthe interval. The portion of rights conveyed can also be a bounded spacewithin the bounded space of the whole. For example, if A owns 100% andconveys 50% to B and 50% to C, the management system can represent therights ownership as B having interval 0 to 0.5, and C having interval0.5 to 1. A will now have nothing. This allows every piece ofinformation related to mineral ownership and/or land use rights to betied back to where the right originated. Thus, for example, everyownership can be related back to specific conveyances and specificsource rights that resulted in the rights conveyed.

In one embodiment, the management system manages rights includingcomputation of rights and ownership. The system can compute thesubdivisions of rights, and determine specifically what rights wereconveyed. In one embodiment, when intervals or other vectors orcomparable mechanism is used, the management system can use set theoryoperations to perform conveyance calculations. Such set operations caninclude set intersections, unions, negations, subtractions, or other settheory operations, or a combination. Thus, the system can operate on anobject or object instance with set operators to perform modifications torights, either generating a new object with the changed information(e.g., a new instance), or modifying an object instance, or both.

It will be understood that an object refers to a defined structure ofproperties, including configuration properties and operationalproperties. The configuration properties define the values associatedwith the fields of the object structure. The operational propertiesrefer to interfaces, calls, permissions, and other elements of an objectthat define its use, operation, interaction, or other implementation. Anobject typically refers to a class or type of component that can becreated in accordance with the defined object structure, and an instancerefers to that structure populated with information in at least one ofthe fields. Typically an instance is given a handle or name or othermechanism to call the object instance for use.

Returning to the discussion of computation of rights and ownership,consider the following example: Assume A owns 100% royalty rights, whichA splits between B and C. A started out with [0-1], and B ends up, forexample, with [0-0.5], and C with [0.5-1]. It will be understood thatthe endpoints of rights ownership intervals can represent asymptotes, inwhich the parties do not have overlapping rights, but the whole rightscan be represented. Assume now that B conveys 50% rights (interval[0.25-0.5]) to D, and C splits its rights to E and F, with E owning[0.5-0.75] and F owning [0.75-1]. D can acquire F's rights and own theroyalty rights on the interval [0.25-0.5, 0.75-1]. As such, D owns 50%of the total royalty for the tract, but the management system canidentify what specific portions are owned by D. Such specificity ofportions is different than traditional methods of tracking, which wouldsimply indicate that D owns 50%, and further information would be neededto try to track down what is represented by D's ownership.

Assume now that G owns the executive rights on the interval [0-0.45,0.95-1], which is coincidentally also 50%. If G executes a lease, tofigure what royalty from the lease applies to D's royalty ownership, inone embodiment, the management system intersects D's royalty intervalwith the leased executive interval of G, to generate the new interval[0.25-0.45, 0.95-1], which is the portion of D's royalty that isaffected by G's lease, or 25% of total tract royalty. By tracking thespecific intervals, the management system easily and accurately tracksthe relationship of G's lease document to D's royalty rights. Again,consider the difference in simply saying that G owns 50% of executiverights, and trying to track down whether and how much of G's 50% affectsD's 50% ownership. What appears on its face as a simple question canhave significant complexity, which can be managed by the systemdescribed herein that generates and manages weighted objects to trackspecific conveyance information.

Referring specifically to mineral rights for one example, it will beunderstood that multiple intervals of different ownership rights andmultiple mineral depths, acreages, geologic formations, minerals, and/orother severances and ownership-related objects can be represented andoperated on using set theory, in accordance with what is describedherein. The contents of a set can be represented in many ways.

In one embodiment, the management system generates an expressionincluding a union of terms, where each term is an intersection ofobjects. In one embodiment, another representation is an intersection ofterms where each term is a union of objects. The unioned termrepresentation can be converted to the intersected term representationwith an algorithm applying the distributive law.

In one embodiment, the following set operations can be applied by themanagement system.

Sets can be unioned by converting all sets to the unioned termrepresentation, then combining all of their terms, then simplifying outredundant terms. Similarly, sets can be intersected by converting allrepresentations to intersections of terms, combining terms, andsimplifying out redundant terms.

A set can be negated by negating each object in the set (such as byapplying a Boolean negation flag to each object in the set, or byperforming a negation operation on the object, if it supports one) andconverting every union to intersection and every intersection to union(e.g., applying deMorgan's law).

Two sets can be “subtracted” (i.e., keep everything in set A that isn'tin set B) by negating set B and intersecting the result with set A.

The examples above do not provide an exclusive list of set operationsthe management system can apply, and are to be understood illustrativelyrather than restrictively. In one embodiment, the management systemincludes set operation capability defined in code, to compute the setsof ownership that each owner ends up with after each legal instrument isapplied to the title chain. As in the simple interval example above, itallows different pieces of ownership to be related back to each othervia intersection and other operations to determine which part of whichownership applies to which part of other ownerships, and thus distributelease royalties and other interests correctly.

FIG. 1A is a representation of an embodiment of a conveyance flowchartillustrating influence of one conveyance document over another portionof the chain of title. Diagram 102 represents a conveyance from A to Band C, a partial conveyance from B to D, a full conveyance from C to Eand F, and a conveyance from F to D. While percentages of ownershiptransfer are not shown, it will be understood that any amount ofconveyance of any rights could be represented by the various conveyancedocuments shown. As illustrated, the last conveyance includes aconveyance from F to D, in which case the conveyance from A to C willinfluence the ownership rights of D.

For purposes of illustration, the elements designated as letters (i.e.,A, B, C, D, E, F) represent objects that indicate ownership associatedwith a named party, where the letters represent the different parties.It will be understood that parties to a transaction or conveyance caninclude natural persons or individuals, groups of individuals, legalentities (e.g., a company, a trust, or other), groups of legal entities,or a combination. The object elements that indicate the ownershipinterest associated with a party are referred to as nodes. Thus, theinitial node 110 indicates the whole ownership interest of party A,which is then conveyed as provided in diagram 102. It will be understoodthat A's ownership interest can be the whole ownership interest of apiece of real property, or could be a partial ownership, where diagram102 only focuses on the dependent or child transactions of A's interest.Thus, diagram 102 does not necessarily indicate all dispositions of landthat is the subject of the illustrated transactions.

For further purposes of illustration, the elements represented bydocument icons represent objects that indicate a conveyance of a part orall of one or more rights. For purposes of convention, if one party hasa node prior to a conveyance, and does not have a node after theconveyance, the conveying party's interest can be considered to becompletely conveyed. For example, node 110 represents A's interests,which are completely divested to B and C through object 112 (conveyanceto B) and object 114 (conveyance to C) as illustrated respectively bynodes 116 and 118. In contrast, when a party includes a node before andafter a conveyance, at least a portion of rights are retained. Forexample, node 116 represents B's interests, which are split via object122 to B (at node 126) and D (at node 128).

It will be observed that separate conveyance documents can be used toconvey to separate parties, or a single conveyance document can conveyto multiple parties. For example, object 112 represents a conveyancedocument that provides rights to B, and is separate from a conveyancedocument represented by object 114 to provide rights to C. Both objects112 and 114 provide rights from A, but are separate documents, and arethus represented by separate objects. In contrast, object 122 representsa conveyance document that provides rights to B and D, and thus, asingle conveyance document as represented by a single objet 122 providesrights to both B and D. Similarly, the rights of C as represented atNode 118 are passed to E (as represented at node 130) and F (asrepresented at node 132) through a common conveyance document asrepresented by object 124.

Diagram 102 also illustrates object 134 to represent a conveyance of F'srights to D at node 135. It will be understood that node 128 representsD's rights as provided by object 122, and node 136 includes more rights,which include the rights represented at node 128 and the rights conveyedby object 134 to D. Thus, a party's right can be subtracted (asrepresented by node 126 of B after the conveyance of object 122) oradded to (as represented by node 146 of D after the conveyance of object134).

In one embodiment, nodes and objects represent different object types.In one embodiment, nodes are part of an object, or objects are part ofthe same object as a node. A node includes structured information torepresent a real party in interest, the type of rights possessed, andone or more ranges indicating the amount of ownership of one or morerights. Thus, nodes can represent one or more or all rights owned by theindicated party. In one embodiment, the ranges represent bounded regionsto indicate specific rights types and amounts of rights. However,bounded spaces indicate not only the amount or percentage of rights, butwhat specific portion of rights are possessed. For example, ownership of[0.3-0.8] is 50% ownership, as is [0.25-0.5, 0.75-1], but the specificportion of rights are different, and will have different sources, andcan be separately managed as described herein.

The document objects represent conveyance document objects. Theconveyance document objects include information to identify theconveying party and the receiving party, and the portion of rightsconveyed. As with node objects, the conveyance objects include boundedspace to identify the specific regions conveyed. It will be understoodthat conveyance documents do not explicitly indicate a bounded spacethat is to be conveyed. Rather, the conveyance documents indicatespecific metes and bounds of the real property rights being transferred.The management system as described herein converts the metes and boundsinto a bounded space to represent the conveyance. Thus, the systemconverts detailed conveyance information into a bounded space of astructured data representation or object of the management system.

Diagram 102 also illustrates another feature of the management systemthat becomes clear in the management system, which is not easilyrecognizable in traditional tracking methods. It will be, observed thatD's rights at node 128 derive solely through object 112 via theconveyance from A to B. Until node 128, object 114 representing theconveyance from A to C has no direct influence on D's rights. Rather,until node 128, object 114 could be considered only to illustrate whatis not conveyed through object 112, and seeing that B retains aninterest, it could be said that D's entire interest is illustrated comesthrough object 112.

However, it will also be observed that all of F's interest is derivedthrough object 114. Therefore, when F makes a conveyance to D throughobject 134, object 114 now influences D's interests at node 136.Therefore, what previously had no relationship now has a relationship oran influence. Reference to an “influence” refers to the fact that rightspossessed by a party are at least partially derived through aninstrument. A relationship refers to either a source (earlier in time)of rights or a receiver (later in time) of rights. The relationshipidentifies that the two objects are connected through chain of title,and the influence can identify the specific amount that is derived orgranted with respect to a source or receiver, respectively.

While the chain of title can trace D's interests at node 136 to aconveyance document represented by object 114, with diagram 102, it canbe readily seen that the conveyance of object 114 influences node 136.Also, the specific amount of influence can be represented by the boundedspaces of the ranges in the objects.

FIG. 1B is a representation of an embodiment of a conveyance flowchartillustrating ownership in accordance with interval sets. Diagram 104provides an alternative view of diagram 102 of FIG. 1A. Morespecifically, diagram 104 illustrates the same conveyance scenario asdiagram 102, and illustrates specific conveyance portions. While equalpercentage conveyances are illustrated, it will be understood that anypercentages could be conveyed. Diagram 104 can be considered onenon-limiting example of diagram 102, as it will be understood that aninfinite combination of portions and conveyances can be represented fordiagram 102.

Referring diagram 104, in one embodiment, a management system representsconveyances via intervals that indicate amount of ownership, as well asthe specific boundaries of the rights ownership. For example, afterconveyance from A, B owns a 50% ownership, and specifically the intervalfrom [0-0.5]. It will be understood that the conveyance documents canrepresent one or more conveyance documents each. A single conveyancedocument can illustrate a conveyance to one party or to multipleparties. Multiple conveyance documents can be used to performconveyances.

Node 140 represents a state or condition where A owns all of a property[0-1]. After conveyances represented by object 142 and object 144, twonew states of possession exist. Namely the states represented by node146 where B owns [0-0.5], and node 148 where C owns [0.5-1].

The conveyance represented by object 150 provides the new ownershipstates of node 154 where B owns [0-0.25], and node 156 where D owns[0.25-0.5]. The conveyance represented by object 152 creates newownership states represented by node 158 where E owns [0.5-0.75], andnode 160 where F owns [0.75-1]. Again, it will be understood that equalportions are represented merely to represent a simple case forillustration, but any range or combination of ranges can be conveyed.

The conveyance represented by object 162 transfers F's interest to D,which changes the state of ownership of D to be represented by node 162where D owns [0.25-0.5, 0.75-1]. It will be observed that object 162does not affect or influence the B's ownership interest in node 154 orE's ownership interest in node 158. Thus, those states of ownershipremain valid, and D's and F's ownership interests have combined in D.

Any combination of scenarios is possible. The example of diagram 104provides a simple illustration of how ownership interests can be trackedacross various branches of a chain of title tree, and accounted for bythe use of bounded space representations for the interests in theobjects.

FIG. 2 is a representation of an embodiment of conveyance information inaccordance with interval sets where a management system computesrelationships based on set operations. System 200 illustrates twoconveyance chains and an operation of the management system based onthose two chains. Thus, system 200 illustrates how the management systemcan utilize set operators to compute interests managed as boundedspaces.

As illustrated, system 200 includes a conveyance chain for royaltyrights from A to B and C, from B to D, from C to E and F, and from F toD. System 200 also includes a conveyance chain to represent an executiveright. In one embodiment, the management system represents theconveyances based on intervals. For the royalty rights, consider ascenario in which A conveys [0-0.5] to B through document (doc) 12, and[0.5-1] to C through document 212, representing the rights as boundedintervals. It will be observed that documents in system 200 are referredto as “documents” rather than objects as in the previous diagrams. Thechange in convention is simply for purposes of illustration, to indicatethat the conveyance object represent actual documents that conveyinterests. Thus, in system 200 the objects that represent the conveyanceof interests are referred to as documents. Such documents within thecontext of system 200 can be understood to be object representations ofthe actual documents. While the actual documents will make conveyancebased on specified portions of land, system 200 represents theconveyances through the objects as bounded space intervals.

The conveyances of document 212 produce ownership states in B and C. Bthen conveys an interest in [0.25-0.5] to D through document 222, and Cconveys interest in [0.5-0.75] to E and an interest in [0.75-1] throughdocument 224. Finally, F conveys an interest in [0.75-1] to D throughdocument 232, and D owns [0.25-0.5, 0.75-1]. The royalty rights aresimple enough to follow, and mirror what is provided in diagram 104.However, when multidimensional issues arise, following the rightsbecomes more complex. For example, the conveyance of G to H canrepresent a lease to H for [0-0.45, 0.95-1] via document 242. In oneembodiment, to determine the effect of G's conveyance to H on D'srights, the management system can compute an intersection of D'sinterval set with H's interval set. In one embodiment, management system250 can perform any of a variety of set operations on the sets todetermine ownership. As illustrated, computation engine 252 ofmanagement system 250 executes the computations including the setoperations to indicate an effect for D of [0.25-0.45, 0.95-1]. In oneembodiment, computation engine 252 computes the intersection of[0.25-0.5, 0.75-1] with [0-0.45, 0.95-1] to result in [0.25-0.45,0.95-1].

Management system 250 with computation engine 252 can compute any typeof interest relationship based on the set operations on the intervals ofthe interacting objects. In the example provided, the object of thestate of H's interest and the object of the state of D's interest arethe interacting objects, and the intervals indicated result in an outputobject that provides for D's rights. Because the intervals preserve thespecific portions of land, and the set operators preserve therelationship of the intervals, the management system can producecomputations that are highly reliable. Furthermore, the rights computedcan be translated back to specific identifiable land portions based onthe understanding of the intervals.

FIG. 3 is a block diagram of an embodiment of a management system.Management system 300 represents elements that can be a part of amanagement system in accordance with any embodiment describedthroughout. Not all components will necessarily be in all managementsystem implementations. Certain management system implementations caninclude elements not illustrated in system 300.

In one embodiment, management system 300 includes server 320 andcustomer 350. Such a management system can operate as a remote serveraccessed in a server-client relationship. In one embodiment, server 320includes management engine 330 or rendering engine 340, or both. In oneembodiment, server 320 provides code to customer 350, which thenexecutes the code at the customer end rather than executing at theserver end. In one embodiment, management system 300 executes the codeat the server end and provides a display to customer 350.

In one embodiment, server 320 includes management engine 330. Managementengine 330 can include code to be executed at the customer. Managementengine 330 can include code to be executed at a server side, remote fromcustomer 350, or over a network from customer. It will be understoodthat remote from the customer refers to executing on different hardwarethan the hardware with which a customer user interfaces. Managementengine 330 can be or include a computation engine. In one embodiment,management engine 330 includes interval generator 332, rights setgenerator 334, one or more set operator engines 336, and computationengine 338. In one embodiment, reference to an engine can refer to theexecution of a function or routine by computing hardware. Thus, the coderepresenting the function or the routine or call can configure and guidethe execution of the processing hardware to generate a transformation ofdata from one state to another.

In one embodiment, computation engine 338 can include set operators 336.Interval generator 332 enables management engine 330 to generateinterval objects to track specific bounded ownership rights. In oneembodiment, rights set generator 334 and rights sets enable managementengine 330 to manage rights as sets of rights, which can then beoperated on in accordance with set operations by set operators. Setoperators 336 represent the ability or the engine of management engine330 to perform set operations to manage land use rights, including themultidimensional issues associated with land use rights tracking. Setoperators 336 can include code to perform specific set operations.Computation engine 338 enables management engine 330 to perform the setoperations to compute ownership of rights in multiple dimensions.

In one embodiment, server 320 includes rendering engine 340. In oneembodiment, rendering engine 340 includes workflow generator 342, whichcan enable rendering engine 340 to use conveyance information togenerate a graphical representation of ownership after the conveyances.In one embodiment, workflow generator 342 can generate multipledifferent types of workflow representations. For example, in oneembodiment, a standard workflow can show conveyance documents andrelationship between them and the relationship of the conveyancedocuments to the parties of the conveyances. Other workflows, such as atree structure, a timing workflow, or other workflows can be created.The workflow can be thought of as a mapping or indexing of conveyanceinformation. In one embodiment, a workflow can include standardconveyance document layout information layered with party information.

In one embodiment, rendering engine 340 includes relationship generator344. Relationship generator 344 enables rendering engine 340 to generateand display relationship information in the graphical representation. Inone embodiment, relationship generator 344 enables rendering engine 340to highlight influence of conveyance documents along the chain of title.For example, in one embodiment, management system 300 as executed atcustomer 350 generates an interactive graphical representation viarendering engine 340, and a user can select a conveyance document byclicking or hovering over the document, or through other interaction.Thus, in one embodiment, selection of a conveyance document canillustrate relationship data, including influence of the conveyancedocument on other conveyances or ownership or a combination.

In one embodiment, customer 350 includes one or more management engineinterfaces 352. Management engine interface 352 at customer 350 canenable the customer to download code from server 320 to execute themanagement engine functions described with respect to management engine330 of server 320. In one embodiment, customer 350 can operate offlineafter receiving code from server 320. In one embodiment, customer 350includes one or more rendering engine interfaces 354. Rendering engine354 interface enables customer 350 to execute the functions describedwith respect to the relationship rendering engine described with respectto rendering engine 340 of server 320.

In one embodiment, customer 350 includes document or informationinterface 356, which can enable a user to upload conveyance informationinto management system 300. The conveyance documents 310 representconveyance information that can be inputted into the management system.In one embodiment, some conveyance information is input into server 320directly, and can be used as the basis for conveyance informationrepresentations at customer. In one embodiment, all conveyanceinformation is input via the customer conveyance information or documentinterface 356. In one embodiment, information input locally at customer350 is only used locally (e.g., customer 350 can download functions fromserver 320). In one embodiment, information input locally at customer350 can be used at server 320 to generate data or data objects or datarepresentations at the server that are sent back to customer 350.Customer 350 includes graphical display 358, which can include graphicalrepresentation information generated by management system 300 (whethercomputed at server 320, at customer 350, or both) for the conveyanceinformation and the ownership information generated. In one embodiment,rendering engine 340 displays information generated by management engine300.

In one aspect, a method for land use rights management includes:representing each of multiple land use rights in an object as a boundedspace, where a portion of a whole right is a specifically designatedsubspace within the bounded space; and managing land use rightsconveyances through object interactions as subdivisions of whole orpartial subspaces within the bounded space, including performing setoperations on bounded spaces of interacting objects to compute thesubdivisions.

In one embodiment, representing each of the multiple land use rights asa bounded space further comprises representing the land use rights asobjects having the bounded space, and representing a subspace as anobject having a specifically designated interval portion of the boundedspace, including defined starting and ending points of the interval topreserve the specific right conveyed. In one embodiment, managing theland use rights conveyances further comprises performing a set operationon separate subspaces to compute a subdivision conveyed. In oneembodiment, performing the set tracking the land use rights conveyancesfurther comprises performing the set operation comprises performing aunion operation between two or more subspaces. In one embodiment,performing the set tracking the land use rights conveyances furthercomprises performing the set operation comprises performing anintersection operation between two or more subspaces. In one embodiment,managing the land use rights conveyances further comprises trackingconveyances based on a combination of at least two of: right type,x-axis and y-axis tract dimensions, z-axis land depth, mineral type, andtime. In one embodiment, managing the land use rights conveyancesfurther comprises tracking conveyances based on all of: right type,x-axis and y-axis tract dimensions, z-axis land depth, mineral type, andtime. In one embodiment, managing the land use rights conveyancescomprises computing a subdivision conveyed based on right typeintervals, x-axis tract dimension intervals, y-axis tract dimensionintervals, z-axis land depth intervals, mineral type intervals, and timeintervals.

In one aspect, a computing device for land use management includes: amemory device to store data related to land use rights conveyances; anda processor to generate multiple objects to represent the land userights conveyances, including to represent each of multiple land userights in an object as a bounded space, where a portion of a whole rightis a specifically designated subspace within the bounded space; and tomanage land use rights conveyances through object interactions assubdivisions of whole or partial subspaces within the bounded space,including the execution of set operations on bounded spaces of objectsto compute the subdivisions.

In one embodiment, the processor is to represent the land use rights asobjects having the bounded space, and represent a subspace as an objecthaving a specifically designated interval portion of the bounded space,including defined starting and ending points of the interval to preservethe specific right conveyed. In one embodiment, the processor is tomanage the land use rights conveyances including to perform a setoperation on separate subspaces to compute a subdivision conveyed. Inone embodiment, the processor is to perform a union operation betweentwo or more subspaces. In one embodiment, the processor is to perform anintersection operation between two or more subspaces. In one embodiment,the processor is to manage the land use rights conveyances including tomanage conveyances based on a combination of at least two of: righttype, x-axis and y-axis tract dimensions, z-axis land depth, mineraltype, and time. In one embodiment, the processor is to manage the landuse rights conveyances including to manage conveyances based on all of:right type, x-axis and y-axis tract dimensions, z-axis land depth,mineral type, and time. In one embodiment, the processor is to managethe land use rights conveyances including to compute a subdivisionconveyed based on right type intervals, x-axis tract dimensionintervals, y-axis tract dimension intervals, z-axis land depthintervals, mineral type intervals, and time intervals.

In one aspect, a method includes: computing land use rights conveyancesas conveyances of specified intervals of a whole land use right, whereeach interval includes a starting and ending point within the whole landuse right, the conveyances based on conveyance instruments; generating agraphical representation of the conveyance instruments, includingrepresenting the conveyance instruments ordered in accordance withspecific rights intervals affected by the respective conveyanceinstruments; and generating relationship lines between graphicalrepresentations of conveyance instruments, each relationship lineindicating an influence of the conveyance instrument on one or moreother conveyance instruments to which it is connected, the influencebased on an amount of land use rights conveyed by the conveyanceinstrument.

In one embodiment, generating the graphical representation furthercomprises generating a flowchart of conveyance instruments. In oneembodiment, generating the relationship lines comprises generating arelationship line between representations of two conveyance instrumentsto indicate an influence per interval for at least one right type, andfor one or more of: x-axis tract dimension, y-axis tract dimension,z-axis land depth, mineral type, or time.

FIG. 4 is a representation of an embodiment of a treehouse view. Diagram400 illustrates treehouse view 402. In treehouse view 402, the partiesto a document are illustrated together in a box, and each separateconveyance document can have a different box illustrating the resultingownership, as represented by intervals. Thus, each document orconveyance is represented as a separate transaction in treehouse view402. In treehouse view 402, the oldest transaction or the sourcetransactions can be set at the “top” of the page, and worked down to thenewest transactions. In one embodiment, such a flow from top to bottomcan be reversed.

As illustrated, transaction 410 provides a conveyance from A to B and C.In one embodiment, the management system can generate transaction 410and the other transactions as separate objects, or as object containers,with documents and rights states for various parties being elementswithin the container. Transaction 420 illustrates a conveyance from C toD. It will be understood that management system can manage rights thatpass through conveyance documents as well as operations of law(succession, inheritance, or other operation). While a specific documentis not illustrated in transaction 430, interests of B and C pass to A,E, and F through a single transaction, or a series of relatedtransactions. In one embodiment, the management and view can beconfigurable to provide the desired type of illustration. Transaction440 illustrates a conveyance of rights from C. The receiving party isnot illustrated, but can be include in the representation if known.

FIG. 5 is a representation of an alternative embodiment of a treehouseview. Diagram 500 represent treehouse view 502, which illustrates anembodiment of a visualization where residual rights information can berepresented in a particular box, such as the circle in the bottom box oftransaction 530. Thus, for example, transaction 510 represents aconveyance from A to B and C. Transaction 520 represents a conveyancefrom B to D and E. It will be understood that A and C retain rights asillustrated in transaction 520. In transaction 530, C conveys rights toA and F, while A already had rights previously. Thus, the circle canrepresent the combination of rights that reside in A after theconveyance of transaction 530, and include the previous rights orinterests.

FIG. 6 is an embodiment of a flow diagram of a process for computingland use rights based on conveyance information. One possible processflow 600 for rights computation or ownership computation can occur asfollows. In one embodiment, the management system can configure theproperty such as by receiving input information on names and informationabout a real property, 602. Such information may also include anoriginal grant of rights, which is typically from a government.

In one embodiment, for each conveyance related to the property, 604, themanagement system receives conveyance information, 606. For example, theuser may input information about the conveyance. As another example, thesystem can access preloaded information or historical documents or otherelectronic information. The system generates one or more rights objectsrelated to the conveyance and the parties to the conveyance, 608. Theobjects can include intervals or bounded spaces. In one embodiment, theobjects can include or be organized into interval set information, 610.The management system can organize or manage the intervals/objects withset operations.

In one embodiment, for each conveyance, the management system candetermine if the conveyance affects other rights, such as rights ownedby other individuals or other rights, or both, related to the rightsconveyed, 612. If other rights are affected, 614 YES branch, in oneembodiment, the management system can compute the affected rights orgenerate a relationship to the other rights or a combination, 616. If noother rights are affected, 614 NO branch, or after computing the effectof the conveyance on other rights, in one embodiment, the systemgenerates ownership results indicating rights ownership, 618. If theconveyance evaluated is the last conveyance, 620 YES branch, thecomputation for the chain of title can finish. If the last conveyancehas not been reached, 620 NO branch, the system can continue to processother conveyance information (returning to 606) and continue until allconveyance information is processed.

FIG. 7 is an embodiment of a flow diagram of a process for generating agraphical rendering of land use rights information. In one embodiment, amanagement system generates graphical representation(s) of conveyanceinformation. Process 700 represents a flow of operation for generating agraphical representation of conveyance information. In one embodiment,the system receives conveyance information and rights calculations, 702.In one embodiment, the management system includes a computation engineto make the calculations. In one embodiment, the management systemincludes integrated components that perform computations and generategraphical representations.

In one embodiment, the computation engine or the rendering engine or acombination generates conveyance relationships for the mapped conveyanceinformation, 704. For example, the relationships can indicate how aconveyance document influences or affects rights associated with theconveyance and rights outside the direct conveyance. For example, aconveyance earlier in time will influence conveyances later in time,since a party cannot convey more than they have rights to convey.

In one embodiment, the system selects a view type, 706. The selectioncan be in response to an interactive request by a user. The system canrender the graphical information in accordance with the selected viewtype, 708. A non-limiting list of view types can include a chain oftitle flowchart 710, a treehouse view that groups parties with eachconveyance information to represent the full effects of the conveyanceon rights 712, a layered view including documents and parties 714, atimeline view 716, an influence highlight, 718, or another view 720, ora combination. Timeline view 716 can represent the conveyances based onthe timing of the conveyances. Influence highlight 718 can illustratethe effects of a conveyance on other conveyances or parties or both inthe chain of title. In one embodiment, the system can support one ormore other views 720.

In one embodiment, the system determines if there should be a change tothe selected view, 722. For example, a user may interact with thegraphical representation and select a change to the view type, or to thedata to be viewed. In one embodiment, if there is no view change to bemade, 724 NO branch, the system can continue to monitor for viewchanges, 722. In one embodiment, if there is a view change, 724 YESbranch, the system can compute a new organization of the conveyance datafor rendering, 726, and render in accordance with the selected viewtype, 708.

FIG. 8A is a representation of an embodiment of a standard graphicalconveyance view. Diagram 802 represents a standard or compact view ofconveyance information, with parties to conveyances represented in boxesillustrating states of ownership, and document objects illustrating theconveyance information, with relationships represented by linesconnecting document objects and party ownership states and otherdocuments that come later in time, which directly derive from thedocument objects.

The parties to the conveyances are represented across the bottom inalphabetical order, but can be grouped in any of a number of differentways. Different groupings could include, but are not limited to:timeline order, order of percentage ownership, order of relationship(e.g., where parties related by conveyance are illustrated next to eachother), or some other order.

The State starts as 100% owner of all rights. Object 812 represents aconveyance of mineral rights. The dashed line to State illustrates theconnection to the party “State” at the bottom. Object 812 can conveysome rights, while others are retained by State. Objects 822, 824, 826,828, and 830 illustrate other transfers. In the view of diagram 802, theparties to the conveyances and the specifics of the conveyance are notillustrated, but other views can show some or all of such information.The view of diagram 802 simply illustrates the objects that representconveyances or conveyance instruments, and the resulting or presentrights or interests in light of all conveyances.

While the specific percentages shown are not necessarily important, theyprovide an illustration of the complexities of tracking rights. Forexample, Executive rights, Mineral rights, Leases, Royalties,Participating and Non-Participating Royalty rights, or other interests,or a combination can all be separately conveyed for separate portions.In one embodiment, diagram 802 illustrates percentage interests, but itcan be understood that the percentages are based on tracking andmanagement of actual portions (e.g., via intervals or bounded spaces).Thus, in the simple view of diagram 802, the final percentages may besufficient for the view, but the actual portions can be tracked by themanagement system in accordance with any embodiment described herein. Itwill be understood that each right can be represented as separatebounded spaces, and operated on separately. For related or intersectingrights, the management system can perform computations to computeinterests based on different bounded spaces.

In one embodiment, different types of rights can be displayed above andbelow a dashed line or other separator to illustrate the differentinterests. As an example, certain interests granted to A in object 822,which are then separated with object 830 can provide interests for D viaobjects 842 and 844, while maintaining certain rights for A. The otherparties (B, C, and State) do not include any of the lower rights and areshown having null sets of interest.

It will be observed that in one embodiment, objects are aligned withparties represented. All parties represented either have a presentinterest (as of the time of the generation of the view), or had aninterest. It will be understood that a “present” interest can berelative. For example, in one embodiment, the management system includesa filter component to select a specific period of time, and representall transactions and interests starting from a period of time and endingat another selected period of time. Thus, a present interest refers toan interest that occurs within the timeline.

FIG. 8B is a representation of an embodiment of a standard graphicalconveyance view showing highlighted relationships. Diagram 804 providesanother illustration of diagram 802, and all the documents andconveyances are considered to be the same. The view of diagram 804provides additional information through the selection of document object830 by a user. Selection of object 830 can cause the system to highlightthe object representing the conveyance document, and highlight itsrelationships. The relationships are highlighted from object 830 toother documents and to parties. For example, the system can highlightthe source relationship of object 830 to object 822, the sourcerelationship of object 830 to object 828, the child relationship (orresulting interest relationship) in A (of which there are actually two),and the resulting interest relationship from object 830 to object 842.The resulting interest relationship indicates that a conveyance documentis the source of rights that a party possesses that permits either acontinuing interest or the ability to convey an interest to anotherparty. In one embodiment, a user can select further information toidentify more details about the conveyances and resulting ownershiprights.

FIGS. 9A-9B illustrate a representation of an embodiment of a graphicallayered view. The layered view of diagrams 902 and 904 represent thesame information as illustrated in diagrams 802 and 804. The use of thesame information is for purposes of illustration as to how the differentviews can be structured, and is not limiting in any way. In a layeredview, the parties and their resulting ownership rights are layeredbetween the conveyance documents. Thus, diagrams 902 and 904 includeother objects to illustrate states of ownership.

Thus, State conveys rights to A via object 912, and A has a presentinterest at that moment of 100% mineral rights. With object 922, Aconveys rights to B, as illustrated. Diagram 902 also illustrates theconveyance and resulting rights from object 924, object 926, and object928. With the layered view, a user has more detail to trace informationthrough the chain of title, instead of simple the final state ofinterests. The conveyance by object 930 continues into diagram 904 ofFIG. 9B. Similar to the above diagrams, diagram 904 illustrates thefinal interests of the various parties. Object 930 grants rights to D,which are split with object 932 between A and D, and the conveyance ofobject 934 affirms the rights to D.

It will be observed that the diagrams illustrate certain rights prefixedby an exclamation operation (I), for example, !H1-L:25% for A in diagram904. The ! operator can be understood as indicating all interest exceptfor what is designated. Thus, A has interest in everything exceptH1-L:25%. Other conventions could be used.

FIG. 10 is a representation of an embodiment of a graphical conveyanceview illustrating the timing of conveyances. As with diagrams 902 and904, diagram 1000 represents the same information as provided in thestandard view of diagram 802, but with timing information.

The timing of conveyances can change the location of where parties areillustrated. With more complex rights and conveyance situations, therecan be more variation in the timing of when parties received theirrights, and would look different than what is illustrated in diagram1000. It will be observed that with timing information, diagram 1000illustrates objects 1012, 1022, 1024, 1026, 1028, 1030, 1042, and 1044in the same relative locations as provided in diagram 802. However, nowthe interest objects are shown in different relative locationsconsistent with the alignment of when the interests were passed. Thus,the interests of State and C can be determined after object 1026, andremain set at that point. The interest of B occurs later, after object1028. The interest of A occurs after object 1030. On the lower portionof the diagram, the interests of State, A, B, and C are known afterobject 1042. The interests of D are known after object 1044.

FIG. 11 is a representation of an embodiment of a graphical ownershipreport. In the ownership report, all ownership rights are illustrated.In one embodiment, the system can display ownership view 1100 inresponse to an interaction with a user, such as a mouse “hover,” or aclick or other selection. On the left, the negative interests can beseen, which indicates that all rights are owned except what are shown.On the right are positive ownership interests, which displaysaffirmative interests. Ownership view 1100 can include “navigation”elements, such as selectable items to refresh the view, export theinformation, or close or exit the view.

In one embodiment, the management system displays ownership view 1100 asan overlay over a different view, such as a popup window or popup view.In one embodiment, ownership view 1100 is displayed as a separate view.While percentage information is illustrated in ownership view 1100, inone embodiment, specific ownership ranges could be illustrated. In oneembodiment, ownership view 1100 can illustrate specific ownershipsegments, referring to specific plot information indicated by conversionof bounded space information to physical plot information.

FIG. 12 is a representation of an embodiment of a graphical runsheetreport. The runsheet report indicates when conveyances occurred. In oneembodiment, the system can display runsheet view 1200 in response to aninteraction with a user, such as a mouse “hover,” or a click or otherselection. Runsheet view 1200 can include “navigation” elements, such asselectable items to refresh the view, export the information as aspreadsheet or export one or more files of the information, or close orexit the view.

In one embodiment, the management system displays runsheet view 1200 asan overlay over a different view, such as a popup window or popup view.In one embodiment, runsheet view 1200 is displayed as a separate view.Runsheet 1200 illustrates the information of conveyances by type ofinstrument, parties affected by the instrument, and the date. It will beunderstood that multiple Grantees can be listed together. It will beunderstood that the management system can generate a separate runsheetfor the same plot of land for different rights.

FIG. 13 is a representation of an embodiment of pseudocode for aconveyance management engine. Pseudocode 1300 provides one simpleexample of functional code operations for creating an object, includingcomputing rights interests as properties for the object. The managementsystem can be said to include and execute the code. In practice a pieceof computer hardware executes the operations. The simplified example ofpseudocode 1300 is to be understood as illustrative, but not limiting.Other functions can be included. The functions illustrated can beexecuted by different function calls. There is no limitation on theorder of the operations of the lines of code, except that linesdependent on other functions or information will occur after suchinformation is obtained or function is performed.

At line 1302, the function is opened for creating an object. In oneembodiment, some or all of the object creation functions can becallable. In one embodiment, object creation functions can be called inresponse to a conveyance document or conveyance object, and the systemwill compute new or modified interests in light of the conveyance. Inone embodiment, one or more elements or conditions are included as inputto create the object. At line 1304, the code identifies the namesassociated with the object. For a conveyance object, the names willinclude the conveying and receiving parties. For an ownership stateobject, the name will be the name of the party whose ownership interestis being computed.

At line 1306, the code can identify the property the object applies to.At line 1308, the code can identify the property rights or interests ofthe identified parties (i.e., names). It will be understood that one ormultiple rights or interests could be implicated. For an ownership nodeobject, the rights can be conveyed through multiple different documents,or a combination of a document and a previous state of ownership rightsfor the same party. For a conveyance document object, the document canconvey multiple different types of rights.

At line 1310, the code generates the rights sets as ranges or intervals.The ranges refer to the bounded spaces referenced throughout. Each rightcan be separately identified as a bounded range or series of ranges. Atline 1312, the code can perform set operations to define the objectrights. For example, the code can take rights from a previous rightsstate and combine them (either additively or subtractively, depending onthe object type and the position of the party) with the modification ornew rights of the instant conveyance.

At line 1314, the code can generate a new instance of the object typewith the defined rights that are computed. In one embodiment, the codeuses an object class as a starting point for object creation. In oneembodiment, the code uses another object instance as a starting pointfor object creation. The created object can inherit the properties ofthe parent object, subject to the modifications of the conveyance. Inone embodiment, at line 1316, the code creates or generates chain oftitle relationships. Such chain of title relationships can berepresented as pointers or calls or handles or other mechanism toanother object managed by the management system. Thus, the managementsystem can trace objects in a structured view, such as those illustratedabove, to represent the chain of title. At line 1318, the code ends thecreate object functions.

FIG. 14 is a representation of an embodiment of pseudocode for a displayof a conveyance management engine. Pseudocode 1400 provides one simpleexample of functional code operations for displaying an object,including rights interests managed as bounded space. The managementsystem can be said to include and execute the code. In practice a pieceof computer hardware executes the operations. The simplified example ofpseudocode 1400 is to be understood as illustrative, but not limiting.Other functions can be included. The functions illustrated can beexecuted by different function calls. There is no limitation on theorder of the operations of the lines of code, except that linesdependent on other functions or information will occur after suchinformation is obtained or function is performed.

At line 1402, the function is opened for displaying an object. In oneembodiment, some or all of the object displaying functions can becallable. In one embodiment, object display functions can be called inresponse to interaction of a user with a graphical display, or creationof an object, or a combination. In one embodiment, the system willcompute new or modified interests in light of a conveyance, and update agraphical representation in realtime. In one embodiment, one or moreelements or conditions are included as input to create the object. Atline 1404, the code generates an object GUI (graphical user interface)for the object type to be displayed. For example, object types caninclude conveyance document objects, rights states objects whichillustrate an instance of a party's interests, or other objects, such asdisplay objects or containers.

At line 1406, the code can identify relationships for the object such assource relationships. For highlighting display changes, therelationships can also include child relationships. At line 1408, thecode can identify source and child objects. It will be understood thatas represented in lines 1406 and 1408, the relationships refer torelationships to states of interest, and the source and child objectsrefer to sources of rights and conveyances of rights. The terminologyhere is simply for purposes of illustration, and is not limiting. Theoperation of lines 1406 and 1408 are to identify a present state ofinterest, and sources and grants of interests that might affect thepresent state of interest.

At line 1410, the code can compute the rights sets as ranges orintervals. The ranges refer to the bounded spaces referenced throughout.Each right can be separately identified as a bounded range or series ofranges. At line 1412, the code can generate graphical elements toillustrate the chain of title, such as lines or curves to connect anobject to another object, which was identified in lines 1406 or 1408 ora combination. In one embodiment, in line 1414, if the management systemdetects an interaction with a graphical representation, it can call thefunctions of the display object to perform operations in response to theinteraction. In one embodiment, the operations in response to theoperation results in calling the display object functions to display adifferent type of view. In one embodiment, as illustrated at line 1416,the code can highlight relationships in response to selections by auser. In one embodiment, the display object function can render adisplay with more detailed information. At line 1418, the interactionfunction ends. At line 1420, the display object functions end.

FIG. 15 is a block of an embodiment of a conveyance object with weightedrights management. Object 1500 represents an example of an object inaccordance with embodiments of objects described throughout. Object 1500is intended to illustrate a simplified view of structured data used tomanage land use rights information. Other properties and functions canbe included. Not every object instance will include all functions ordata. Object 1500 generically represents an object, and different typesof objects can be implemented in a management system.

In one embodiment, object 1500 includes rights properties 1510. Therights properties define the interests of a party. In one embodiment,right properties 1510 includes an owner name or an identification of aparty 1512. Owner name 1512 represents an ownership. Instance of object1500 that represent conveyances can include multiple instances of rightsproperties 1510, such as to represent all parties of the conveyance.

In one embodiment, rights properties 1510 includes rights sets 1514,which identify what interests are owned by owner name 1512. Rightsproperties 1510 include rights ranges 1516, which represent boundedspace or intervals. Rights ranges 1516 provides a specificrepresentation for the management system of how much and what specificrights are owned. Rights are operable by the management system viaoperators interface 1518, which represents that rights properties 1510includes ranges that can be computed by set operators to compute newrights that preserve the quantity and portion information through theintervals. Thus, set operators can modify one or more intervals based ona type of interaction with a different set of one or more intervals.

In one embodiment, object 1500 includes chain information 1520. Chaininformation 1520 represents data, functions, interfaces, or acombination that enables the management system to associate object 1500with other objects in chain of title relationships. The chain of titlerelationships will be understood to be within the context of themanagement system. Thus, there is no requirement that every relationshipbe exactly traceable to a specific real property document. For example,relationships between conveyance document objects and interest nodeobjects (or objects representing the state of ownership), are derived bythe management system, to represent the results of the documents. In thephysical world, only the documents themselves exist, and the managementsystem generates the relationships and interest node objects torepresent information to a user as a summary or understanding of theresults of the real world documents.

In one embodiment, chain information 1520 can include source 1522, whichrepresents a source of rights. Source 1522 refers to one or more objectsthat represent the source of rights set out in rights properties 1510.In one embodiment, chain information 1520 can include children 1524,which represents rights conveyed to other parties. Children 1524 refersto one or more other objects that represent the receipt of rightsconveyed from a party identified by rights properties 1510. In oneembodiment, chain information 1520 includes relationships 1526, whichcan include all relationships or interactions with other objects thatare not specifically source 1522 or children 1524. Such relationshipscan include placeholders, positioning, timing information, or any otherrelationship.

FIG. 16 is a block diagram of an embodiment of a computing system inwhich real property rights management can be implemented. System 1600represents a computing device in accordance with any embodimentdescribed herein, and can be a laptop computer, a desktop computer, atablet computer, a server, a gaming or entertainment control system, ascanner, copier, printer, routing or switching device, embeddedcomputing device, a smartphone, a wearable device, an internet-of-thingsdevice or other electronic device.

System 1600 includes processor 1610, which provides processing,operation management, and execution of instructions for system 1600.Processor 1610 can include any type of microprocessor, centralprocessing unit (CPU), graphics processing unit (GPU), processing core,or other processing hardware to provide processing for system 1600, or acombination of processors. Processor 1610 controls the overall operationof system 1600, and can be or include, one or more programmablegeneral-purpose or special-purpose microprocessors, digital signalprocessors (DSPs), programmable controllers, application specificintegrated circuits (ASICs), programmable logic devices (PLDs), or thelike, or a combination of such devices.

In one embodiment, system 1600 includes interface 1612 coupled toprocessor 1610, which can represent a higher speed interface or a highthroughput interface for system components that needs higher bandwidthconnections, such as memory subsystem 1620 or graphics interfacecomponents 1640. Interface 1612 can represent a “north bridge” circuit,which can be a standalone component or integrated onto a processor die.Where present, graphics interface 1640 interfaces to graphics componentsfor providing a visual display to a user of system 1600. In oneembodiment, graphics interface 1640 can drive a high definition (HD)display that provides an output to a user. High definition can refer toa display having a pixel density of approximately 100 PPI (pixels perinch) or greater, and can include formats such as full HD (e.g., 1080p),retina displays, 4K (ultra high definition or UHD), or others. In oneembodiment, the display can include a touchscreen display. In oneembodiment, graphics interface 1640 generates a display based on datastored in memory 1630 or based on operations executed by processor 1610or both. In one embodiment, graphics interface 1640 generates a displaybased on data stored in memory 1630 or based on operations executed byprocessor 1610 or both.

Memory subsystem 1620 represents the main memory of system 1600, andprovides storage for code to be executed by processor 1610, or datavalues to be used in executing a routine. Memory subsystem 1620 caninclude one or more memory devices 1630 such as read-only memory (ROM),flash memory, one or more varieties of random access memory (RAM) suchas DRAM (dynamic RAM), or other memory devices, or a combination of suchdevices. Memory 1630 stores and hosts, among other things, operatingsystem (OS) 1632 to provide a software platform for execution ofinstructions in system 1600. Additionally, applications 1634 can executeon the software platform of OS 1632 from memory 1630. Applications 1634represent programs that have their own operational logic to performexecution of one or more functions. Processes 1636 represent agents orroutines that provide auxiliary functions to OS 1632 or one or moreapplications 1634 or a combination. OS 1632, applications 1634, andprocesses 1636 provide software logic to provide functions for system1600. In one embodiment, memory subsystem 1620 includes memorycontroller 1622, which is a memory controller to generate and issuecommands to memory 1630. It will be understood that memory controller1622 could be a physical part of processor 1610 or a physical part ofinterface 1612. For example, memory controller 1622 can be an integratedmemory controller, integrated onto a circuit with processor 1610.

While not specifically illustrated, it will be understood that system1600 can include one or more buses or bus systems between devices, suchas a memory bus, a graphics bus, interface buses, or others. Buses orother signal lines can communicatively or electrically couple componentstogether, or both communicatively and electrically couple thecomponents. Buses can include physical communication lines,point-to-point connections, bridges, adapters, controllers, or othercircuitry or a combination. Buses can include, for example, one or moreof a system bus, a Peripheral Component Interconnect (PCI) bus, aHyperTransport or industry standard architecture (ISA) bus, a smallcomputer system interface (SCSI) bus, a universal serial bus (USB), oran Institute of Electrical and Electronics Engineers (IEEE) standard1394 bus (commonly referred to as “Firewire”).

In one embodiment, system 1600 includes interface 1614, which can becoupled to interface 1612. Interface 1614 can be a lower speed interfacethan interface 1612. In one embodiment, interface 1614 can be a “southbridge” circuit, which can include standalone components and integratedcircuitry. In one embodiment, multiple user interface components orperipheral components, or both, couple to interface 1614. Networkinterface 1650 provides system 1600 the ability to communicate withremote devices (e.g., servers or other computing devices) over one ormore networks. Network interface 1650 can include an Ethernet adapter,wireless interconnection components, cellular network interconnectioncomponents, USB (universal serial bus), or other wired or wirelessstandards-based or proprietary interfaces. Network interface 1650 canexchange data with a remote device, which can include sending datastored in memory or receiving data to be stored in memory.

In one embodiment, system 1600 includes one or more input/output (I/O)interface(s) 1660. I/O interface 1660 can include one or more interfacecomponents through which a user interacts with system 1600 (e.g., audio,alphanumeric, tactile/touch, or other interfacing). Peripheral interface1670 can include any hardware interface not specifically mentionedabove. Peripherals refer generally to devices that connect dependentlyto system 1600. A dependent connection is one where system 1600 providesthe software platform or hardware platform or both on which operationexecutes, and with which a user interacts.

In one embodiment, system 1600 includes storage subsystem 1680 to storedata in a nonvolatile manner. In one embodiment, in certain systemimplementations, at least certain components of storage 1680 can overlapwith components of memory subsystem 1620. Storage subsystem 1680includes storage device(s) 1684, which can be or include anyconventional medium for storing large amounts of data in a nonvolatilemanner, such as one or more magnetic, solid state, or optical baseddisks, or a combination. Storage 1684 holds code or instructions anddata 1686 in a persistent state (i.e., the value is retained despiteinterruption of power to system 1600). Storage 1684 can be genericallyconsidered to be a “memory,” although memory 1630 is typically theexecuting or operating memory to provide instructions to processor 1610.Whereas storage 1684 is nonvolatile, memory 1630 can include volatilememory (i.e., the value or state of the data is indeterminate if poweris interrupted to system 1600). In one embodiment, storage subsystem1680 includes controller 1682 to interface with storage 1684. In oneembodiment controller 1682 is a physical part of interface 1614 orprocessor 1610, or can include circuits or logic in both processor 1610and interface 1614.

Power source 1602 provides power to the components of system 1600. Morespecifically, power source 1602 typically interfaces to one or multiplepower supplies 1604 in system 1602 to provide power to the components ofsystem 1600. In one embodiment, power supply 1604 includes an AC to DC(alternating current to direct current) adapter to plug into a walloutlet. Such AC power can be renewable energy (e.g., solar power) powersource 1602. In one embodiment, power source 1602 includes a DC powersource, such as an external AC to DC converter. In one embodiment, powersource 1602 or power supply 1604 includes wireless charging hardware tocharge via proximity to a charging field. In one embodiment, powersource 1602 can include an internal battery or fuel cell source.

In one embodiment, system 1600 includes elements of a land usemanagement or manager 1690 (alternately referred to as management system1690) in accordance with any embodiment described throughout. In oneembodiment, system 1600 represents a computing device that executesmanagement system 1690. In one embodiment, system 1600 represents acomputing device through which a user accesses a server that execute themanagement system. Management system 1690 exists within system 1600 ascomponents for execution. As illustrated, code, data, and objects can bestored within memory subsystem 1620 for execution. Processor 1610executes the code and objects, and uses the data to perform thefunctions of the management system. Thus, components of managementsystem 1690 within system 1600 configure the hardware components ofsystem 1600 to provide the functions described in embodiments of amanagement system described throughout. It will be understood thateither as a server or as an accessing device, system 1600 can access theother side of the operation (i.e., either the client side or the serverside) via network interface 1650. In one embodiment, system 1600 storesone or more components for execution of land use management 1690.

FIG. 17 is a block diagram of an embodiment of a mobile device in whichreal property rights management can be implemented. Device 1700represents a mobile computing device, such as a computing tablet, amobile phone or smartphone, a wireless-enabled e-reader, wearablecomputing device, an internet-of-things device or other mobile device,or an embedded computing device. It will be understood that certain ofthe components are shown generally, and not all components of such adevice are shown in device 1700.

Device 1700 includes processor 1710, which performs the primaryprocessing operations of device 1700. Processor 1710 can include one ormore physical devices, such as microprocessors, application processors,microcontrollers, programmable logic devices, or other processing means.The processing operations performed by processor 1710 include theexecution of an operating platform or operating system on whichapplications and device functions are executed. The processingoperations include operations related to I/O (input/output) with a humanuser or with other devices, operations related to power management,operations related to connecting device 1700 to another device, or acombination. The processing operations can also include operationsrelated to audio I/O, display I/O, or other interfacing, or acombination. Processor 1710 can execute data stored in memory. Processor1710 can write or edit data stored in memory.

In one embodiment, system 1700 includes one or more sensors 1712.Sensors 1712 represent embedded sensors or interfaces to externalsensors, or a combination. Sensors 1712 enable system 1700 to monitor ordetect one or more conditions of an environment or a device in whichsystem 1700 is implemented: Sensors 1712 can include environmentalsensors (such as temperature sensors, motion detectors, light detectors,cameras, chemical sensors (e.g., carbon monoxide, carbon dioxide, orother chemical sensors)), pressure sensors, accelerometers, gyroscopes,medical or physiology sensors (e.g., biosensors, heart rate monitors, orother sensors to detect physiological attributes), or other sensors, ora combination. Sensors 1712 can also include sensors for biometricsystems such as fingerprint recognition systems, face detection orrecognition systems, or other systems that detect or recognize userfeatures. Sensors 1712 should be understood broadly, and not limiting onthe many different types of sensors that could be implemented withsystem 1700. In one embodiment, one or more sensors 1712 couples toprocessor 1710 via a frontend circuit integrated with processor 1710. Inone embodiment, one or more sensors 1712 couples to processor 1710 viaanother component of system 1700.

In one embodiment, device 1700 includes audio subsystem 1720, whichrepresents hardware (e.g., audio hardware and audio circuits) andsoftware (e.g., drivers, codecs) components associated with providingaudio functions to the computing device. Audio functions can includespeaker or headphone output, as well as microphone input. Devices forsuch functions can be integrated into device 1700, or connected todevice 1700. In one embodiment, a user interacts with device 1700 byproviding audio commands that are received and processed by processor1710.

Display subsystem 1730 represents hardware (e.g., display devices) andsoftware components (e.g., drivers) that provide a visual display forpresentation to a user. In one embodiment, the display includes tactilecomponents or touchscreen elements for a user to interact with thecomputing device. Display subsystem 1730 includes display interface1732, which includes the particular screen or hardware device used toprovide a display to a user. In one embodiment, display interface 1732includes logic separate from processor 1710 (such as a graphicsprocessor) to perform at least some processing related to the display.In one embodiment, display subsystem 1730 includes a touchscreen devicethat provides both output and input to a user. In one embodiment,display subsystem 1730 includes a high definition (HD) display thatprovides an output to a user. High definition can refer to a displayhaving a pixel density of approximately 100 PPI (pixels per inch) orgreater, and can include formats such as full HD (e.g., 1080p), retinadisplays, 4K (ultra high definition or UHD), or others. In oneembodiment, display subsystem includes a touchscreen display. In oneembodiment, display subsystem 1730 generates display information basedon data stored in memory or based on operations executed by processor1710 or both.

I/O controller 1740 represents hardware devices and software componentsrelated to interaction with a user. I/O controller 1740 can operate tomanage hardware that is part of audio subsystem 1720, or displaysubsystem 1730, or both. Additionally, I/O controller 1740 illustrates aconnection point for additional devices that connect to device 1700through which a user might interact with the system. For example,devices that can be attached to device 1700 might include microphonedevices, speaker or stereo systems, video systems or other displaydevice, keyboard or keypad devices, or other I/O devices for use withspecific applications such as card readers or other devices.

As mentioned above, I/O controller 1740 can interact with audiosubsystem 1720 or display subsystem 1730 or both. For example, inputthrough a microphone or other audio device can provide input or commandsfor one or more applications or functions of device 1700. Additionally,audio output can be provided instead of or in addition to displayoutput. In another example, if display subsystem includes a touchscreen,the display device also acts as an input device, which can be at leastpartially managed by I/O controller 1740. There can also be additionalbuttons or switches on device 1700 to provide I/O functions managed byI/O controller 1740.

In one embodiment, I/O controller 1740 manages devices such asaccelerometers, cameras, light sensors or other environmental sensors,gyroscopes, global positioning system (GPS), or other hardware that canbe included in device 1700, or sensors 1712. The input can be part ofdirect user interaction, as well as providing environmental input to thesystem to influence its operations (such as filtering for noise,adjusting displays for brightness detection, applying a flash for acamera, or other features).

In one embodiment, device 1700 includes power management 1750 thatmanages battery power usage, charging of the battery, and featuresrelated to power saving operation. Power management 1750 manages powerfrom power source 1752, which provides power to the components of system1700. In one embodiment, power source 1752 includes an AC to DC(alternating current to direct current) adapter to plug into a walloutlet. Such AC power can be renewable energy (e.g., solar power, motionbased power). In one embodiment, power source 1752 includes only DCpower, which can be provided by a DC power source, such as an externalAC to DC converter. In one embodiment, power source 1752 includeswireless charging hardware to charge via proximity to a charging field.In one embodiment, power source 1752 can include an internal battery orfuel cell source.

Memory subsystem 1760 includes memory device(s) 1762 for storinginformation in device 1700. Memory subsystem 1760 can includenonvolatile (state does not change if power to the memory device isinterrupted) or volatile (state is indeterminate if power to the memorydevice is interrupted) memory devices, or a combination. Memory 1760 canstore application data, user data, music, photos, documents, or otherdata, as well as system data (whether long-term or temporary) related tothe execution of the applications and functions of system 1700. In oneembodiment, memory subsystem 1760 includes memory controller 1764 (whichcould also be considered part of the control of system 1700, and couldpotentially be considered part of processor 1710). Memory controller1764 includes a scheduler to generate and issue commands to controlaccess to memory device 1762.

Connectivity 1770 includes hardware devices (e.g., wireless or wiredconnectors and communication hardware, or a combination of wired andwireless hardware) and software components (e.g., drivers, protocolstacks) to enable device 1700 to communicate with external devices. Theexternal device could be separate devices, such as other computingdevices, wireless access points or base stations, as well as peripheralssuch as headsets, printers, or other devices. In one embodiment, system1700 exchanges data with an external device for storage in memory or fordisplay on a display device. The exchanged data can include data to bestored in memory, or data already stored in memory, to read, write, oredit data.

Connectivity 1770 can include multiple different types of connectivity.To generalize, device 1700 is illustrated with cellular connectivity1772 and wireless connectivity 1774. Cellular connectivity 1772 refersgenerally to cellular network connectivity provided by wirelesscarriers, such as provided via GSM (global system for mobilecommunications) or variations or derivatives, CDMA (code divisionmultiple access) or variations or derivatives, TDM (time divisionmultiplexing) or variations or derivatives, LTE (long termevolution—also referred to as “4G”), or other cellular servicestandards. Wireless connectivity 1774 refers to wireless connectivitythat is not cellular, and can include personal area networks (such asBluetooth), local area networks (such as WiFi), or wide area networks(such as WiMax), or other wireless communication, or a combination.Wireless communication refers to transfer of data through the use ofmodulated electromagnetic radiation through a non-solid medium. Wiredcommunication occurs through a solid communication medium.

Peripheral connections 1780 include hardware interfaces and connectors,as well as software components (e.g., drivers, protocol stacks) to makeperipheral connections. It will be understood that device 1700 couldboth be a peripheral device (“to” 1782) to other computing devices, aswell as have peripheral devices (“from” 1784) connected to it. Device1700 commonly has a “docking” connector to connect to other computingdevices for purposes such as managing (e.g., downloading, uploading,changing, synchronizing) content on device 1700. Additionally, a dockingconnector can allow device 1700 to connect to certain peripherals thatallow device 1700 to control content output, for example, to audiovisualor other systems.

In addition to a proprietary docking connector or other proprietaryconnection hardware, device 1700 can make peripheral connections 1780via common or standards-based connectors. Common types can include aUniversal Serial Bus (USB) connector (which can include any of a numberof different hardware interfaces), DisplayPort including MiniDisplayPort(MDP), High Definition Multimedia Interface (HDMI), Firewire, or othertype.

In one embodiment, system 1700 includes elements of a land usemanagement or manager 1790 (alternately referred to as management system1790) in accordance with any embodiment described throughout. Typically,system 1700 would represent a computing device through which a useraccesses a server that execute the management system. However, system1700 can represent one embodiment of a computing device that executesmanagement system 1790. Management system 1790 exists within system 1700as components for execution. As illustrated, code, data, and objects canbe stored within memory subsystem 1760 for execution. Processor 1710executes the code and objects, and uses the data to perform thefunctions of the management system. Thus, components of managementsystem 1790 within system 1700 configure the hardware components ofsystem 1700 to provide the functions described in embodiments of amanagement system described throughout. It will be understood thateither as a server or as an accessing device, system 1700 can access theother side of the operation (i.e., either the client side or the serverside) via network connectivity component 1770.

FIG. 18 is a block diagram of an embodiment of a multi-node network inwhich real property rights management can be implemented. System 1800represents a data center or cloud server. In one embodiment, system 1800represents a server farm. In one embodiment, system 1800 represents adata cloud or a processing cloud. System 1800 can include one or morecomputing devices in accordance with system 1600.

One or more clients 1802 make requests over network 1804 to system 1800.Network 1804 represents one or more local networks, or wide areanetworks, or a combination. Clients 1802 can be human or machineclients, which generate requests for the execution of operations bysystem 1800. System 1800 executes applications or data computation tasksrequested by clients 1802.

In one embodiment, system 1800 includes one or more racks, whichrepresent structural and interconnect resources to house andinterconnect multiple computation nodes. In one embodiment, rack 1810includes multiple nodes 1830. In one embodiment, rack 1810 hostsmultiple blade components 1820. Hosting refers to providing power,structural or mechanical support, and interconnection. Blades 1820 canrefer to computing resources on printed circuit boards (PCBs), where aPCB houses the hardware components for one or more nodes 1830. In oneembodiment, blades 1820 do not include a chassis or housing or other“box” other than that provided by rack 1810. In one embodiment, blades1820 include housing with exposed connector to connect into rack 1810.In one embodiment, system 1800 does not include rack 1810, and eachblade 1820 includes a chassis or housing that can stack or otherwisereside in close proximity to other blades and allow interconnection ofnodes 1830.

System 1800 includes fabric 1870, which represents one or moreinterconnectors for nodes 1830. In one embodiment, fabric 1870 includesmultiple switches 1872 or routers or other hardware to route signalsamong nodes 1830. Additionally, fabric 1870 can couple system 1800 tonetwork 1804 for access by clients 1802. In addition to routingequipment, fabric 1870 can be considered to include the cables or portsor other hardware equipment to couples nodes 1830 together. In oneembodiment, fabric 1870 has one or more associated protocols to managethe routing of signals through system 1800. In one embodiment, theprotocol or protocols is at least partly dependent on the hardwareequipment used in system 1800.

As illustrated, rack 1810 includes N blades 1820. In one embodiment, inaddition to rack 1810, system 1800 includes rack 1850. As illustrated,rack 1850 includes M blades 1860. M is not necessarily the same as N;thus, it will be understood that various different hardware equipmentcomponents could be used, and coupled together into system 1800 overfabric 1870. Blades 1860 can be the same or similar to blades 1820.Nodes 1830 can be any type of node as described herein, and are notnecessarily all the same type of node. System 1800 is not limited tobeing homogenous, nor is it limited to not being homogenous.

For simplicity, only the node in blade 1820[0] is illustrated in detail.However, other nodes in system 1800 can be the same or similar. At leastsome nodes 1830 are computation nodes, with processor 1832 and memory1840. A computation node refers to a node with processing resources(e.g., one or more processors) that executes an operating system and canreceive and process one or more tasks. In one embodiment, at least somenodes 1830 are storage server nodes with a server as processingresources 1832 and memory 1840. A storage server refers to a node withmore storage resources than a computation node, and rather than havingprocessors for the execution of tasks, a storage server includesprocessing resources to manage access to the storage nodes within thestorage server.

In one embodiment, node 1830 includes interface controller 1834, whichrepresents logic to control access by node 1830 to fabric 1870. Thelogic can include hardware resources to interconnect to the physicalinterconnection hardware. The logic can include software or firmwarelogic to manage the interconnection. In one embodiment, interfacecontroller 1834 is or includes a host fabric interface (HFI). Node 1830includes memory subsystem 1840, which provides storage services for datato be computed by processors 1832. Processor 1832 can include one ormore separate processors. Each separate processor can include a singleprocessing unit, a multicore processing unit, or a combination. Theprocessing unit can be a primary processor such as a CPU (centralprocessing unit), a peripheral processor such as a GPU (graphicsprocessing unit), or a combination. Memory 1840 can be or include memorydevices and a memory controller.

In one embodiment, node 1830 includes land use manager 1880, whichrepresents elements of a land use management system in accordance withany embodiment described throughout. Land use manager 1880 exists withinsystem 1800 as components for execution. As illustrated, code, data, andobjects can be stored within node 1830 for execution. Multiple nodes1830 can include multiple instances of land use manager 1880, orcomponents of land use manager 1880 can be spread across multiple nodes1830. Land use manager 1880 in system 1800 enables the providing of landuse management services over network 1804 to clients 1802.

In one embodiment, the management system can instantaneously detectoverconveyance and strangers in title (i.e., a name that has not beentied back to a conveyance document), or other errors, or a combination,in the chain of title. As stated before, human understanding does notnormally comprehend information in dimensions beyond three. However,representing the conveyances as intervals and sets can enable themanagement system to quickly and correctly identify errors in conveyanceinformation.

In one embodiment, the management system can display information basedon time, percentage ownership, or alphabetical order of conveyornames/aliases, or a combination. In one embodiment, the managementsystem can rearrange the view based on recent conveyances instead ofalphabetical order. In one embodiment, the rendering engine enables therepresentation of information based on individual conveyors. In oneembodiment, the graphical representation is organized based on whichconveyance documents are associated with which individuals or parties.

As explained above, as use rights expand, the traditional methods usedto track actual ownership rights gets exponentially more complex.Current mechanisms for tracking rights are inadequate, and people do nottrack adequately. Traditional conveyance management involves the use ofa number of assumptions that are made when conveying, and based on themultidimensional complexity involved in tracking, such assumptionscannot adequately track rights.

From one perspective, the management system performs indexing of theconveyance information. In one embodiment, the management system sets upindexing with the intervals. In one embodiment, the management systemapplies set operations to intervals rather than traditional sets. Thatenables the system to apply set operations to multidimensionalcomputation problems. In one embodiment, the management system organizesall conveyance information in set form. In one embodiment, withintervals and sets, the specific intervals can be separated viaconveyances. The original conveyances can be preserved to be appliedagainst later conveyances. Such management can prevent “merging” backrights based only on scalar percentages, which could mix conveyances.

In one aspect, a method includes: representing each of multiple land userights as a bounded space, where a portion of a whole right is aspecifically designated subspace within the bounded space; and trackingland use rights conveyances as subdivisions of whole or partialsubspaces within the bounded space, including performing set operationsto compute the subdivisions.

In one embodiment of the method, representing each of the multiple landuse rights as a bounded space further comprises representing the landuse rights as objects having the bounded space, and representing asubspace as an object having a specifically designated interval portionof the bounded space, including defined starting and ending points ofthe interval to preserve the specific right conveyed. In one embodimentof the method, tracking the land use rights conveyances furthercomprises performing a set operation on separate subspaces to compute asubdivision conveyed. In one embodiment of the method, performing theset tracking the land use rights conveyances further comprisesperforming the set operation comprises performing a union operationbetween two or more subspaces. In one embodiment of the method,performing the set tracking the land use rights conveyances furthercomprises performing the set operation comprises performing anintersection operation between two or more subspaces. In one embodimentof the method, tracking the land use rights conveyances furthercomprises tracking conveyances based on all of: right type, x-axis andy-axis tract dimensions, z-axis land depth, mineral type, and time. Inone embodiment of the method, tracking the land use rights conveyancescomprises computing a subdivision conveyed based on right typeintervals, x-axis tract dimension intervals, y-axis tract dimensionintervals, z-axis land depth intervals, mineral type intervals, and timeintervals.

In one aspect, an apparatus includes hardware and/or software componentsto execute operations in accordance with any embodiment of the method.In one aspect, an article of manufacture comprising a computer readablestorage medium having content stored thereon, which when executed by amachine performs operations to execute any embodiment of the method.

In one aspect, a method includes: computing land use rights conveyancesas conveyances of specified intervals of a whole land use right, whereeach interval includes a starting and ending point within the whole landuse right, the conveyances based on conveyance instruments; generating agraphical representation of the conveyance instruments, includingrepresenting the conveyance instruments ordered in accordance withspecific rights intervals affected by the respective conveyanceinstruments; and generating relationship lines between graphicalrepresentations of conveyance instruments, each relationship lineindicating an influence of the conveyance instrument on one or moreother conveyance instruments to which it is connected.

In one embodiment of the method, generating the graphical representationfurther comprises generating a flowchart of conveyance instruments. Inone embodiment of the method, generating the relationship linescomprises generating a relationship line between representations of twoconveyance instruments to indicate an influence per interval for atleast one right type, and for one or more of: x-axis tract dimension,y-axis tract dimension, z-axis land depth, mineral type, or time. In oneembodiment of the method, computing the land use rights conveyancesfurther comprises performing operations in accordance with anyembodiment of the method for computing land use rights.

In one aspect, an apparatus includes hardware and/or software componentsto execute operations in accordance with any embodiment of the method.In one aspect, an article of manufacture comprising a computer readablestorage medium having content stored thereon, which when executed by amachine performs operations to execute any embodiment of the method.

Flow diagrams as illustrated herein provide examples of sequences ofvarious process actions. The flow diagrams can indicate operations to beexecuted by a software or firmware routine, as well as physicaloperations. In one embodiment, a flow diagram can illustrate the stateof a finite state machine (FSM), which can be implemented in hardwareand/or software. Although shown in a particular sequence or order,unless otherwise specified, the order of the actions can be modified.Thus, the illustrated embodiments should be understood only as anexample, and the process can be performed in a different order, and someactions can be performed in parallel. Additionally, one or more actionscan be omitted in various embodiments; thus, not all actions arerequired in every embodiment. Other process flows are possible.

To the extent various operations or functions are described herein, theycan be described or defined as software code, instructions,configuration, and/or data. The content can be directly executable(“object” or “executable” form), source code, or difference code(“delta” or “patch” code). The software content of the embodimentsdescribed herein can be provided via an article of manufacture with thecontent stored thereon, or via a method of operating a communicationinterface to send data via the communication interface. A machinereadable storage medium can cause a machine to perform the functions oroperations described, and includes any mechanism that stores informationin a form accessible by a machine (e.g., computing device, electronicsystem, etc.), such as recordable/non-recordable media (e.g., read onlymemory (ROM), random access memory (RAM), magnetic disk storage media,optical storage media, flash memory devices, etc.). A communicationinterface includes any mechanism that interfaces to any of a hardwired,wireless, optical, etc., medium to communicate to another device, suchas a memory bus interface, a processor bus interface, an Internetconnection, a disk controller, etc. The communication interface can beconfigured by providing configuration parameters and/or sending signalsto prepare the communication interface to provide a data signaldescribing the software content. The communication interface can beaccessed via one or more commands or signals sent to the communicationinterface.

Various components described herein can be a means for performing theoperations or functions described. Each component described hereinincludes software, hardware, or a combination of these. The componentscan be implemented as software modules, hardware modules,special-purpose hardware (e.g., application specific hardware,application specific integrated circuits (ASICs), digital signalprocessors (DSPs), etc.), embedded controllers, hardwired circuitry,etc.

Besides what is described herein, various modifications can be made tothe disclosed embodiments and implementations of the invention withoutdeparting from their scope. Therefore, the illustrations and examplesherein should be construed in an illustrative, and not a restrictivesense. The scope of the invention should be measured solely by referenceto the claims that follow.

What is claimed is:
 1. A method for land use rights management,comprising: representing land use rights as bounded spaces, where awhole land use right is embodied as a computer object having a wholebounded space with an interval from a start point to an end point, and apartial land use right is embodied as a computer object having a partialbounded space as a specifically designated subspace within the wholebounded space of the whole land use right, with the partial boundedspace less than the interval from the start point to the end point;managing land use rights conveyances through interactions of thecomputer objects, including computing a subdivision of land use rightsfor a land use rights conveyance by performing set operations on aninteraction of whole bounded spaces and/or on partial bounded spaces ofa first computer object representing first land use rights with a secondcomputer object representing second land use rights, the subdivision ofland use rights computed for a subdivision of land use rights conveyed;and generating a third computer object from the interaction of the firstcomputer object with the second computer object to represent the landuse rights conveyed.
 2. The method of claim 1, wherein managing the landuse rights conveyances further comprises performing a set operation on apartial bounded space of the first computer object with a partial boundspace of the second computer object to compute the subdivision of landuse rights conveyed.
 3. The method of claim 2, wherein performing theset operation comprises performing a union operation between the partialbounded space of the first computer object and the partial bounded spaceof the second computer object to compute a joinder of land use rightsconveyed.
 4. The method of claim 2, wherein performing the set operationcomprises performing an intersection operation between the partialbounded space of the first computer object and the partial bounded spaceof the second computer object to compute a division of land use rightsconveyed.
 5. The method of claim 1, wherein managing the land use rightsconveyances further comprises tracking conveyances based on acombination of at least two of: right type, x-axis and y-axis tractdimensions, z-axis land depth, mineral type, and time.
 6. The method ofclaim 1, wherein managing the land use rights conveyances furthercomprises tracking conveyances based on all of: right type, x-axis andy-axis tract dimensions, z-axis land depth, mineral type, and time. 7.The method of claim 6, wherein managing the land use rights conveyancescomprises computing a subdivision conveyed based on right typeintervals, x-axis tract dimension intervals, y-axis tract dimensionintervals, z-axis land depth intervals, mineral type intervals, and timeintervals.
 8. A computing device for land use management, comprising: amemory device to store data related to land use rights conveyances; anda processor configured to generate multiple computer objects torepresent the land use rights conveyances, including to represent landuse rights as bounded spaces, where a whole land use right is embodiedas a computer object having a whole bounded space with an interval froma start point to an end point, and a partial land use right is embodiedas a computer object having a partial bounded space as a specificallydesignated subspace within the whole bounded space of the whole land useright, with the partial bounded space less than the interval from thestart point to the end point; the processor configured to manage landuse rights conveyances through interactions of the computer objects,including computation of a subdivision of land use rights for a land userights conveyance by execution of set operations on an interaction ofwhole bounded spaces and/or on partial bounded spaces of a firstcomputer object representing first land use rights with a secondcomputer object representing second land use rights, the subdivision ofland use rights computed for a subdivision of land use rights conveyed;and to generate a third computer object from the interaction of thefirst computer object with the second computer object to represent theland use rights conveyed.
 9. The computing device of claim 8, whereinthe processor is to manage the land use rights conveyances including toperform a set operation on a partial bounded space of the first computerobject with a partial bound space of the second computer object tocompute the subdivision of land use rights conveyed.
 10. The computingdevice of claim 9, wherein the processor is to perform a union operationbetween the partial bounded space of the first computer object and thepartial bounded space of the second computer object to compute a joinderof land use rights conveyed.
 11. The computing device of claim 9,wherein the processor is to perform an intersection operation betweenthe partial bounded space of the first computer object and the partialbounded space of the second computer object to compute a division ofland use rights conveyed.
 12. The computing device of claim 8, whereinthe processor is to manage the land use rights conveyances including tomanage conveyances based on a combination of at least two of: righttype, x-axis and y-axis tract dimensions, z-axis land depth, mineraltype, and time.
 13. The computing device of claim 8, wherein theprocessor is to manage the land use rights conveyances including tomanage conveyances based on all of: right type, x-axis and y-axis tractdimensions, z-axis land depth, mineral type, and time.
 14. The computingdevice of claim 13, wherein the processor is to manage the land userights conveyances including to compute a subdivision conveyed based onright type intervals, x-axis tract dimension intervals, y-axis tractdimension intervals, z-axis land depth intervals, mineral typeintervals, and time intervals.
 15. A non-transitory computer readablestorage medium storing content, which when accessed, providesinstructions to cause a machine to execute a method for land use rightsmanagement, comprising: representing land use rights as bounded spaces,where a whole land use right is embodied as a computer object having awhole bounded space with an interval from a start point to an end point,and a partial land use right is embodied as a computer object having apartial bounded space as a specifically designated subspace within thewhole bounded space of the whole land use right, with the partialbounded space less than the interval from the start point to the endpoint; managing land use rights conveyances through interactions of thecomputer objects, including computing a subdivision of land use rightsfor a land use rights conveyance by performing set operations on aninteraction of whole bounded spaces and/or on partial bounded spaces ofa first computer object representing first land use rights with a secondcomputer object representing second land use rights, the subdivision ofland use rights computed for a subdivision of land use rights conveyed;and generating a third computer object from the interaction of the firstcomputer object with the second computer object to represent the landuse rights conveyed.
 16. The computer readable storage medium of claim15, wherein managing the land use rights conveyances further comprisesperforming a set operation on a partial bounded space of the firstcomputer object with a partial bound space of the second computer objectto compute the subdivision of land use rights conveyed.
 17. The computerreadable storage medium of claim 16, wherein performing the setoperation comprises performing a union operation between the partialbounded space of the first computer object and the partial bounded spaceof the second computer object to compute a joinder of land use rightsconveyed.
 18. The computer readable storage medium of claim 16, whereinperforming the set operation comprises performing an intersectionoperation between the partial bounded space of the first computer objectand the partial bounded space of the second computer object to compute adivision of land use rights conveyed.
 19. The computer readable storagemedium of claim 15, wherein managing the land use rights conveyancesfurther comprises tracking conveyances based on a combination of atleast two of: right type, x-axis and y-axis tract dimensions, z-axisland depth, mineral type, and time.
 20. The computer readable storagemedium of claim 15, wherein managing the land use rights conveyancescomprises computing a subdivision conveyed based on right typeintervals, x-axis tract dimension intervals, y-axis tract dimensionintervals, z-axis land depth intervals, mineral type intervals, and timeintervals.